Method and apparatus for mobile device security

ABSTRACT

A method, non-transitory computer readable medium and apparatus for providing security on a mobile endpoint device are disclosed. For example, the method scans for a radio frequency signal, determines a state of the mobile endpoint device and triggers an alarm on the mobile endpoint device if the radio frequency signal is not detected for a predefined period of time and the state of the mobile endpoint device is an inactive state.

The present disclosure relates generally to mobile device security and,more particularly, to a method and apparatus for detecting mobile deviceproximity to a user and associated security actions thereof.

BACKGROUND

The proliferation of mobile telephones and “smart phones” has made thema part of everyday life for most users. For example, users depend on themobile telephones to store contact information, important documents,personal information, bank account information, schedules, and the like.

In addition, as the mobile telephones and smart phones become moresophisticated, the cost of these devices has steadily increased. As aresult, users may suffer security and financial consequences if theylose their mobile telephone or smart phone.

SUMMARY

In one embodiment, the present disclosure provides a method forproviding security on a mobile endpoint device. For example, the methodscans for a radio frequency signal, determines a state of the mobileendpoint device and triggers an alarm on the mobile endpoint device ifthe radio frequency signal is not detected for a predefined period oftime and the state of the mobile endpoint device is an inactive state.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure can be readily understood by considering thefollowing detailed description in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates one example of a communications network of thepresent disclosure;

FIG. 2 illustrates an example flowchart of one embodiment of a methodfor providing security on a mobile endpoint device; and

FIG. 3 illustrates a high-level block diagram of a general-purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

The present disclosure broadly discloses a method, non-transitorycomputer readable medium and apparatus for providing security on amobile endpoint device. The rise in the use of mobile endpoint devices,such as smart phones, has become so prolific that many users relyheavily on their mobile endpoint device for communications, productivityand entertainment. As a result, users cannot afford to lose or misplacetheir mobile endpoint device and risk losing or exposing all of theirpersonal contact information, email messages, financial information,stored documents, and the like.

Currently, there is no simple and practical way for a mobile endpointdevice to alert a user that he is walking away from his mobile endpointdevice and is about to leave his mobile endpoint device behind. Rather,most technology today is used to help locate a mobile endpoint deviceafter the fact, that is, the user has realized that he has lost hismobile endpoint device and then may use an application to attempt tolocate his mobile endpoint device. One embodiment of the presentdisclosure attempts to prevent users from losing their mobile endpointdevice.

FIG. 1 is a block diagram depicting one example of a communicationsnetwork 100. The communications network 100 may be any type ofcommunications network, such as for example, a traditional circuitswitched network (e.g., a public switched telephone network (PSTN)) or apacket network such as an Internet Protocol (IP) network (e.g., an IPMultimedia Subsystem (IMS) network, an asynchronous transfer mode (ATM)network, a wireless network, a cellular network (e.g., 2G, 3G, and thelike), a long term evolution (LTE) network, and the like) related to thecurrent disclosure. It should be noted that an IP network is broadlydefined as a network that uses Internet Protocol to exchange datapackets. Additional exemplary IP networks include Voice over IP (VoIP)networks, Service over IP (SoIP) networks, and the like.

In one embodiment, the network 100 may comprise a core network 102. Thecore network 102 may be in communication with one or more accessnetworks 120 and 122. The access networks 120 and 122 may include awireless access network (e.g., a WiFi network and the like), a cellularaccess network, a PSTN access network, a cable access network, a wiredaccess network and the like. In one embodiment, the access networks 120and 122 may all be different types of access networks, may all be thesame type of access network, or some access networks may be the sametype of access network and other may be different types of accessnetworks. The core network 102 and the access networks 120 and 122 maybe operated by different service providers, the same service provider ora combination thereof.

In one embodiment, the core network 102 may include an applicationserver (AS) 104 and a database (DB) 106. Although only a single AS 104and a single DB 106 are illustrated, it should be noted that any numberof application servers 104 or databases 106 may be deployed.

In one embodiment, the AS 104 may comprise a general purpose computer asillustrated in FIG. 3 and discussed below. In one embodiment, the DB 106may store personal information of the subscribers of the communicationnetwork 100. In addition, the DB 106 may store secondary endpoint deviceinformation for a subscriber and endpoint device information associatedwith an alternate contact person for the subscriber, as discussed below.

In one embodiment, the access network 120 may be in communication withone or more user endpoint devices (also referred to as “endpointdevices”) 108 and 112. In one embodiment, the access network 122 may bein communication with one or more endpoint devices 114 and 116.

It should be noted that the network 100 has been simplified. Forexample, the network 100 may include other network elements (not shown)such as border elements, routers, switches, policy servers, securitydevices, gateways, a content distribution network (CDN) and the like.

In one embodiment, the endpoint device 108 may be a mobile endpointdevice such as a cellular telephone, a smart phone, a tablet computer, alaptop computer, a netbook, a portable media device (e.g., an iPod®touch or MP3 player), and the like. In one embodiment, the endpointdevice 108 may be configured with near field communications (NFC)capability, e.g., a reader such as an RF reader to receive a signal froma passive or active RF tag. For example, the NFC may be built into theendpoint device 108 or may be an attachment to the endpoint device. Inone embodiment, the endpoint devices 112, 114 and 116 may be any type ofendpoint devices including, for example, a PSTN telephone, a smartphone, a cellular telephone, a laptop, a tablet device, a desktopcomputer, and the like.

In one embodiment, the endpoint device 108 may be in communication witha passive radio frequency (RF) tag 110. The RF tag 110 may be any typeof passive (or active in one embodiment) signaling device compatiblewith NFC. In one embodiment, the endpoint device 108 may be configuredto be associated with a unique RF tag, e.g., the RF tag 110. In otherwords, the endpoint device 108 may be looking for a specific RF signal(or broadly a particular identification signal) from the RF tag 110. Theendpoint device 108 would not try to read RF signals from other RE tagsthat were not registered with it.

In one embodiment, mobile endpoint device security may be provided byusing a combination of the NFC capability of the endpoint device 108 andthe RF tag 110. For example, when the endpoint device 108 is unable toread or detect the RF tag 110, the endpoint device 108 may assume thatthe user has lost the endpoint device 108 and take one or more securityactions until the user can confirm that he has retrieved the endpointdevice 108.

To illustrate by example, the RF tag 110 may be proximate to (e.g.,located on or near) a user or subscriber of the endpoint device 108. Forexample, the RE tag 110 may be placed inside of a pant pocket of theuser or a shirt pocket of the user where the user would typically carryhis endpoint device. In another embodiment, the RF tag 110 may belocated in an accessory of the user that holds the endpoint device 108.For example, the accessory may be a holster, a bag or a purse that theuser may use to carry the endpoint device 108.

As discussed above, the endpoint device 108 is configured with NFC,either built-in or via an attachment. The endpoint device 108 may usethe NFC to read the RF tag 110 or to receive an RF signal emitted by theRF tag 110. In one embodiment, the endpoint device 108 may check for anRF signal from the RF tag 110 continuously or periodically, for example,once a minute, once an hour and the like.

In one embodiment, near field communications may operate within arelatively short distance based on configuration of the near fieldcommunications device, for example within a few inches or less thantwelve inches. As a result, by placing the RE tag 110 in a locationwhere the user carries his endpoint device 108, the endpoint device 108may receive the RF signal from the RF tag 110.

However, when the user removes the endpoint device 108 from the locationwhere the user carries the endpoint device 108, the endpoint device 108may be moved a distance away from the RF tag 110 and be out of range toreceive a signal from the RF tag 110.

In one embodiment, if the endpoint device 108 is out of range of the RFtag 110 for a predefined period of time (e.g., 10 seconds, 30 minutes, 1hour and the like), the endpoint device 108 may activate a securityaction.

In one embodiment, the endpoint device 108 may be removed to be used bythe user. For example, the user may be making a telephone call, browsingthe web, running an application (e.g., a game application or aproductivity application such as a word processing application) orsending a text message. To ensure that the security action is notprematurely activated, the endpoint device 108 may require that theendpoint device 108 is out of range of the RF tag 110 and also in astate that is an inactive state.

In other words, the endpoint device 108 may also monitor its own state.If the endpoint device 108 is in an active state (e.g., being used bythe user as discussed above) then the security action may not beactivated even if the endpoint device 108 has been out of range of theRF tag 110 for greater than the predefined period of time. However, ifthe endpoint device 108 is in an inactive state (e.g., not being used bythe user as discussed above) and has been out of range of the RE tag 110for greater than the predefined period of time, then this may indicatethat the user is about to lose or has lost his endpoint device 108 andthe security action may be activated.

In one embodiment, the active state may be detected when a user isactively operating the endpoint device 108, e.g., making a telephonecall, browsing the Internet, writing an email message, writing a textmessage, executing an application, opening a document and the like. Inone embodiment, the active state may be detected using one or more ofthe sensors on the endpoint device 108. For example, if the endpointdevice 108 detects movement via an accelerometer in the endpoint device108 or detects the user's face via a camera on the endpoint device, thenthe endpoint device may be in an active state. In one embodiment, theactive state may be any state other than a sleep mode.

In one embodiment, the inactive state may be when no activity has beendetected on the endpoint device 108 for a predefined time period, forexample, 5 minutes, 1 hour and the like. In one embodiment, the inactivestate may be when the endpoint device 108 is idling with the screen off,powered down or in a “sleep” mode.

In one embodiment, the security action may include, for example,triggering an alarm, sending a communication with location informationof the endpoint device, locking down the endpoint device and the like.In one embodiment, if the RF signal is not detected for a predefinedtime period and the mobile endpoint device 108 is in an inactive state,then one or more of the above security actions may be activated. Itshould be noted that the security actions described above are onlyexamples and are not intended to be limiting. Other types of securityactions may be used and are within the scope of the present disclosure.

For example, the alarm may be an audible notification (e.g., beeping,ringtones, vibrating, etc.) or customized voice memo to alert the usersthat they are leaving their endpoint device behind. To illustrate, theuser may leave his endpoint device on a table in the restaurant. As heis leaving, the endpoint device 108 does not detect the RF signal forthe predefined period of time and the mobile endpoint device 108 is inan inactive state. As a result, the endpoint device 108 begins beepingloudly to alert the user that he has left his endpoint device. As aresult, the user returns to retrieve the endpoint device. Alternatively,the alarm may be a customized voice memo recorded by the user. Forexample, the user may record a voice memo “Jane Doe, don't leave yourphone!” As a result, the endpoint device may play this customized voicememo when the alarm is triggered.

In one embodiment, the communication may be a message (e.g., a textmessage, an email message) or an automated telephone call. In oneembodiment, the message may include a multimedia attachment. Forexample, the endpoint device 108 may take a photo, record a video clipand/or record a sound clip of its surroundings. The photo, video clipand/or the sound clip may be sent as an attachment with the message. Asa result, clues about the surroundings of where the endpoint device 108is located may help a user determine where the endpoint device 108 islocated. In one embodiment, the endpoint device 108 may take the photo,record the video clip and/or record the sound clip periodically until itis confirmed that the user has recovered the endpoint device 108. As aresult, in case the endpoint device 108 is moved or stolen, the photo,video clip and/or the sound recording would help to track itssurroundings as it changes. In one embodiment, the location informationmay include global positioning satellite (GPS) coordinates or an address(e.g., based on correlated coordinates (e.g., GPS coordinates) to mapinformation) of where the endpoint device 108 is physically located.

In one embodiment, the communication may be sent to a secondary endpointof the user. For example, the secondary endpoint device 112 may be ahome desktop computer of the user and/or the secondary endpoint device114 may be a home telephone. As a result, the endpoint device 108 maysend an email message or a text message to the endpoint device 112 withthe location information or may send an automated telephone call to theendpoint device 114 including the location information.

In one embodiment, the communication may be sent to an alternate contactpredefined by the user. For example, the user may know that he is goingout with his spouse for dinner. As a result, the user predefines hisspouse as an alternate contact and includes a telephone number of hisspouse's endpoint, e.g., the endpoint device 116. This information maybe stored in a local memory of the endpoint device 108 or in the networkin the DB 106. As a result, the endpoint device 108 may send a textmessage or a telephone call having the location information to theendpoint 116 of the user's spouse. Using the above example, as the useris leaving the restaurant with his spouse, the endpoint device 108 maytext message the endpoint device 116 of the user's spouse. The spousemay then notify the user that he has left his endpoint device 108 behindat the restaurant and the user may go back to retrieve his endpointdevice 108.

In one embodiment, the endpoint device 108 may send a communication to anetwork service provider of the endpoint device 108. For example, theendpoint device 108 may send a communication to the AS 104. The AS 104may look up the user's secondary endpoint device information and/or theuser's alternate contact information in the DB 106. Then the AS 104 mayproceed to contact the user's secondary endpoint devices and/or theuser's alternate contact as described above.

In one embodiment, the endpoint device 108 may lock itself down as asecurity action. For example, only 911 calls may be made with theendpoint device 108, but no other services, features or applications maybe accessed.

In one embodiment, all of the security actions may be activatedsimultaneously. In another embodiment, the security actions may beactivated in gradations based upon multiple predefined time periods ofnot receiving an RF signal from the RF tag 110.

For example, if no RF signal is received within a first predefined timeperiod (e.g., 10 second) and the endpoint device 108 is in an inactivestate, then endpoint device 108 may trigger an alarm. If no RF signal isreceived within a second predefined time period (e.g., 30 minutes) andthe endpoint device 108 is still in an inactive state, then the endpointdevice 108 may send a message with location information using any one ofthe methods discussed above. If no RF signal is received within a thirdpredefined time period (e.g., 1 hour) and the endpoint device 108 isstill in an inactive state, then the endpoint device may lock itselfdown and so forth.

In one embodiment, the security actions may stay activated until a userhas confirmed that he has retrieved the endpoint device 108. Forexample, the confirmation may include entering a security code, enteringa password, providing an answer to a security question and the like viathe endpoint device 108. Once the confirmation is received, the endpointdevice 108 may deactivate any security action that was activated.

In one embodiment, the security actions may be configurable by the user.In other words, the user may turn the security actions on or off at anytime. For example, the user may be studying at a library and has hisendpoint device out on a table out of range of the RF tag 110. As aresult, to prevent the security actions from being activated while theuser is not using the endpoint device 108, the user may turn off thesecurity actions on the endpoint device 108.

In one embodiment, the security actions may be turned off for apredefined period of time. Using the above example, the user may knowthat he will be studying for approximately two hours. However, afterstudying for two hours the user may have a greater chance of forgettinghis endpoint device 108 on the table. As a result, the user may set thepredefined period of time to two hours for turning off the securityactions. Once the two hours have elapsed, the endpoint device 108 mayactivate one or more of the security actions if no RF signal is receivedfor a predetermined time period and the endpoint device 108 is in aninactive state.

For example, if the predefined period of time for detecting the RFsignal is 10 seconds, after two hours the endpoint device 108 wouldbegin scanning for the RF signal. One or more security actions may beactivated if no signal is detected after 10 second after the two hourperiod of time set by the user and the endpoint is in an inactive state.

As a result, embodiments of the present disclosure help to prevent auser from leaving his endpoint device or losing his endpoint device andimplementing security features if the endpoint device is left behind orlost. In other words, embodiments of the present disclosure attempt toproactively prevent a user from losing his endpoint device, rather thansimply helping to find the endpoint device after the fact.

FIG. 2 illustrates a flowchart of a method 200 for providing security ona mobile endpoint device. In one embodiment, the method 200 may beperformed by the endpoint device 108 having NFC capabilities or ageneral purpose computing device having NFC capabilities as illustratedin FIG. 3 and discussed below.

The method 200 begins at step 202. At step 204, the method 200 scans foran RF signal. For example, a user may place a passive RF tag in alocation where he carries his mobile endpoint device, such as his pantpocket, a holster, a purse and the like. In one embodiment, the mobileendpoint device scans for the RF signal emitted by the passive RF tagvia the mobile endpoint device's NFC capability to ensure that themobile endpoint device is in the possession of the user. In oneembodiment, the passive RE tag is registered with the mobile endpointdevice such that the mobile endpoint device is only scanning for aparticular RF signal.

In one embodiment, the mobile endpoint device may scan continuously. Inanother embodiment, the mobile endpoint device may scan periodically,for example, once a minute, once an hour and the like.

At step 206, the method 200 determines a state of the mobile endpointdevice. For example, the mobile endpoint device may be in an activestate or in an inactive state. In one embodiment, the active state maybe when a user is operating the mobile endpoint device, e.g., making atelephone call, browsing the Internet, writing an email message, writinga text message, executing an application, opening a document and thelike. For example, if the mobile endpoint device detects movement via anaccelerometer in the mobile endpoint device or detects the users facevia a camera on the endpoint device, then the endpoint device may be inan active state. In one embodiment, the active state may be any stateother than a sleep mode.

In one embodiment, the inactive state may be when no activity has beendetected on the mobile endpoint device for a predefined time period, forexample, 5 minutes, 1 hour and the like. In one embodiment, the inactivestate may be when the mobile endpoint device is powered down, in an“idle” mode or in a “sleep” mode.

At step 208, the method 200 determines if the RF signal was detectedwithin a predefined period of time. If the RF signal was detected, themethod 200 loops back to step 204 to scan for the RF signal.

However, if no RF signal was detected, the method 200 proceeds to step210. At step 210, the method 200 determines if the mobile endpointdevice is in an inactive state. If the mobile endpoint device is not inan active state (e.g., the user is operating the mobile endpointdevice), then the method loops back to step 204 to scan for the RFsignal. However, if the mobile endpoint device is in an inactive state,then the method 200 proceeds to step 212.

At step 212, the method 200 activates a security action, e.g., triggersan alarm. This is because at step 208 and step 210, the method 200determined that no RF signal was detected within the predefined periodof time and that the mobile endpoint device is in an inactive state. Thealarm may be an audible alarm as described above.

In one embodiment, the method 200 may also activate other securityactions at step 212 simultaneously with the triggering of the alarm. Anyof the security actions described above may be activated.

In one embodiment, the method 200 may activate other security actions ona graduated basis via optional steps 214-224. If the optional steps214-224 are not performed, then the method 200 may proceed to step 226.

At step 226, the method 200 receives a confirmation that the mobileendpoint is back in the possession of the user. For example, theconfirmation may include entering a security code, entering a password,providing an answer to a security question and the like via the mobileendpoint device. Once the confirmation is received, the mobile endpointdevice may deactivate any security action that was activated.

However, if the optional steps 214-224 are performed, from step 212 themethod 200 may proceed to step 214. At step 214, the method 200determines if an RF signal was detected within a second predefinedperiod of time. In one embodiment, the second predefined period of timemay be a longer period of time than the period of time in step 208. Forexample, the predefined period of time for step 208 may be relativelyshort such as 15 seconds. The second predefined period of time may belonger, for example, 30 minutes.

If an RF signal was detected at step 214, then the method 200 proceedsback to step 204 to scan for an RF signal. However, if no RF signal wasdetected then the method 200 proceeds to step 216.

At step 216, the method 200 determines if the mobile endpoint device isin an inactive state. If the mobile endpoint device is not in aninactive state, then the method 200 proceeds back to step 204 to scanfor an RF signal. However, if the mobile endpoint device is in an activestate, the method 200 proceeds to step 218.

At step 218, the method 200 may send a communication that includeslocation information of the mobile endpoint device. For example, if theuser did not return to pick up his mobile endpoint device after step212, the mobile endpoint device may determine that it is lost andattempts to notify the user via a message with location information suchas an address or GPS coordinates. As discussed above, the communicationmay be a text message, an email message or an automated telephone callto an alternate endpoint device of the user, to an alternate contact orto the network service provider.

At step 220, the method 200 determines if an RF signal was detectedwithin a third predefined period of time. In one embodiment, the thirdpredefined period of time may be a longer period of time than the periodof time in step 208 and the second predefined period of time in step214. For example, the third predefined period of time may be 1 hour.

If an RF signal was detected at step 220, then the method 200 proceedsback to step 204 to scan for an RF signal. However, if no RF signal wasdetected then the method 200 proceeds to step 222.

At step 222, the method 200 determines if the mobile endpoint device isin an inactive state. If the mobile endpoint device is not in aninactive state, then the method 200 proceeds back to step 204 to scanfor an RF signal. However, if the mobile endpoint device is in an activestate, the method 200 proceeds to step 224.

At step 224, the method 200 may lock down the mobile endpoint device.For example, only 911 calls may be made with the endpoint device 108,but no other services, features or applications may be accessed.

The method 200 then may proceed to step 226. At step 226, as notedabove, the method 200 receives a confirmation that the mobile endpointis back in the possession of the user. For example, the confirmation mayinclude entering a security code, entering a password, providing ananswer to a security question and the like via the mobile endpointdevice. Once the confirmation is received, the mobile endpoint devicemay deactivate any security action that was activated. The method 200ends at step 228.

It should be noted that although not explicitly specified, one or moresteps of the method 200 described above may include a storing,displaying and/or outputting step as required for a particularapplication. In other words, any data, records, fields, and/orintermediate results discussed in the methods can be stored, displayed,and/or outputted to another device as required for a particularapplication. Furthermore, steps or blocks in FIG. 2 that recite adetermining operation, or involve a decision, do not necessarily requirethat both branches of the determining operation be practiced. In otherwords, one of the branches of the determining operation can be deemed asan optional step.

FIG. 3 depicts a high-level block diagram of a general-purpose computersuitable for use in performing the functions described herein. Asdepicted in FIG. 3, the system 300 comprises a hardware processorelement 302 (e.g., a CPU), a memory 304, e.g., random access memory(RAM) and/or read only memory (ROM), a module 305 for providing securityon a mobile endpoint device, and various input/output devices 306, e.g.,near field communications capability, an accelerometer, a gyro, acamera, a light sensor, a microphone, a compass, pressure sensor, atemperature sensor, storage devices, including but not limited to, atape drive, a floppy drive, a hard disk drive or a compact disk drive, areceiver, a transmitter, a speaker, a display, a speech synthesizer, anoutput port, and a user input device (such as a keyboard, a keypad, amouse, and the like).

It should be noted that the present disclosure can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general purposecomputer or any other hardware equivalents, e.g., computer readableinstructions pertaining to the method(s) discussed above can be used toconfigure a hardware processor to perform the steps of the abovedisclosed method. In one embodiment, the present module or process 305for providing security on a mobile endpoint device can be loaded intomemory 304 and executed by hardware processor 302 to implement thefunctions as discussed above. As such, the present method 305 forproviding security on a mobile endpoint device as discussed above inmethod 200 (including associated data structures) of the presentdisclosure can be stored on a non-transitory (e.g., tangible orphysical) computer readable storage medium, e.g., RAM memory, magneticor optical drive or diskette and the like.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for providing security on a mobileendpoint device, comprising: scanning, by a processor, for a radiofrequency signal; determining, by the processor, a state of the mobileendpoint device; triggering, by the processor, an alarm on the mobileendpoint device if the radio frequency signal is not detected for apredefined period of time and the state of the mobile endpoint device isan inactive state; and if the radio frequency signal is not detected fora second predefined period of time and the state of the mobile endpointdevice is the inactive state, sending, by the processor, a communicationthat includes location information of the mobile endpoint device.
 2. Themethod of claim 1, wherein the scanning is performed by a near fieldcommunications reader on the mobile endpoint device.
 3. The method ofclaim 1, wherein the radio frequency signal is emitted by a radiofrequency tag located proximate to a user of the mobile endpoint device.4. The method of claim 1, wherein the alarm comprises an audiblenotification.
 5. The method of claim 1, wherein the communication issent to an alternate endpoint device of a user.
 6. The method of claim1, wherein the communication is sent to an alternate contact that ispredefined by a user.
 7. The method of claim 1, wherein thecommunication is sent to a network service provider and the networkservice provider is tasked with contacting a user of the mobile endpointdevice.
 8. The method of claim 1, wherein the communication comprises amessage.
 9. The method of claim 8, wherein the message includes amultimedia attachment.
 10. The method of claim 1, wherein thecommunication comprises an automated telephone call.
 11. The method ofclaim 1, further comprising: if the radio frequency signal is notdetected for a third predefined period of time and the state of themobile endpoint device is the inactive state, locking the mobileendpoint device.
 12. A non-transitory computer-readable medium storing aplurality of instructions which, when executed by a processor, cause theprocessor to perform operations for providing security on a mobileendpoint device, the operations comprising: scanning for a radiofrequency signal; determining a state of the mobile endpoint device;triggering an alarm on the mobile endpoint device if the radio frequencysignal is not detected for a predefined period of time and the state ofthe mobile endpoint device is an inactive state; and if the radiofrequency signal is not detected for a second predefined period of timeand the state of the mobile endpoint device is the inactive state,sending a communication that includes location information of the mobileendpoint device.
 13. The non-transitory computer-readable medium ofclaim 12, wherein the scanning is performed by a near fieldcommunications reader on the mobile endpoint device.
 14. Thenon-transitory computer-readable medium of claim 12, wherein the radiofrequency signal is emitted by a radio frequency tag located proximateto a user of the mobile endpoint device.
 15. The non-transitorycomputer-readable medium of claim 12, wherein the communication is sentto an alternate endpoint device of a user.
 16. The non-transitorycomputer-readable medium of claim 12, wherein the communication is sentto an alternate contact that is predefined by a user.
 17. Thenon-transitory computer-readable medium of claim 12, wherein thecommunication is sent to a network service provider and the networkservice provider is tasked with contacting a user of the mobile endpointdevice.
 18. An apparatus for providing security on a mobile endpointdevice, comprising: a processor; and a computer-readable medium storinga plurality of instructions which, when executed by the processor, causethe processor to perform a operations, the operations comprising:scanning for a radio frequency signal; determining a state of the mobileendpoint device; and triggering an alarm on the mobile endpoint deviceif the radio frequency signal is not detected for a predefined period oftime and the state of the mobile endpoint device is an inactive state;and if the radio frequency signal is not detected for a secondpredefined period of time and the state of the mobile endpoint device isthe inactive state, sending a communication that includes locationinformation of the mobile endpoint device.
 19. The non-transitorycomputer-readable medium of claim 12, further comprising: if the radiofrequency signal is not detected for a third predefined period of timeand the state of the mobile endpoint device is the inactive state,locking the mobile endpoint device.
 20. The apparatus of claim 18,further comprising: if the radio frequency signal is not detected for athird predefined period of time and the state of the mobile endpointdevice is the inactive state, locking the mobile endpoint device.